| Name | The field is required on all asset types. It must be a unique name different from any other asset in CenterScape |
| Asset Tag | This is a reference for the RF Code asset tag associated with the asset. The tag must be eligible to be assigned to an asset. The tag management section of this document describes how to make tags eligible for association to an asset. |
| Description | The is a general field used to describe an asset. Most all asset types have this field. |
| Assigned To | This field assigns an asset to another asset. The asset types that have this field are designed to be assigned to either a Summary Location like a Rack or Room, or in some cases Server Blades to a Blade Chassis. If Assigned To is used, the Assigned Location attribute will be automatically updated to the same Assigned Location as the Summary Location Asset. Assigned To is preferable to Assigned Location for Assets with an Assigned To field particularly since moving the Summary Location Asset to another *Assigned Location will move all the assets assigned to the Summary Location Asset to the new Assigned Location. For example, moving a Rack that has server assigned to it to a new location will move all assets that have that rack as their *Assigned Location to the new location as well. Assets that do not have the Assigned To field should use Assigned Location. If using the Assigned To attribute, the Assigned Location attribute will be overridden after the Asset is saved. Therefore, Assigned Location should be left blank if Assigned To is used. |
| Assigned Location | This field assigns an asset directly to a Location. The Assigned Location is used to determine where an asset belongs and is used by the Location Verified attribute to compare the Detected Location and SSI Location to determine whether an asset is physically located in its intended location. The Assigned Location can be overridden if the Assigned To attribute is used. If an asset has an entry for the Assigned To attribute, changing the Assigned Location may be overridden by the Update Assigned Location calculated attribute. It is recommended that the Assigned To field be blank before manually updating Assigned Location. |
| Operational Status | The Operational Status field is a Constrained list of possible statuses for an Asset. Its used to describe the state of an asset. Generally, the status value of “Operational” is useful to combine with reports or alerts to pay attention to exceptions. For example an asset in Procurement may not be detected so its situation would be different than an asset that is Operational that is not detected. For something like a Temperature Sensor alarms can be configured to alert only if a Temperature Sensor is marked as operational, which allows installation without generating new alarms. The default Operational Status is Installed. |
| Detected Location | Detected Location is the location that an asset is detected to be in based on data supplied by Zone Manager. This field cannot be updated except by Zone Manager and is available to any asset with an RF Code Asset Tag assigned. The special location “Uknown Location” is used when no location rules match a tag that can be observed by readers or when no readers can receive beacons from a tag. |
| Online Status | The Online Status is set to null if there is no asset tag assigned to an asset. If any reader is receiving beacons from a tag then Online Status will be “yes” even if there are no location rules that match. Online Status will be “no” if an asset has a valid Asset Tag, but no readers can observe the tag. |
| Location Path | The location path is the fully location tree path to the Assigned Location. This field is generated by CenterScape and cannot be modified as its value is derived from Assigned Location. For example: Location / USA / Texas / Austin / Austin Datacenter / Austin Server Room 01 / Rack 1 |
| Last Update Time | Last update time is a timestamp that indicated the last time Asset Attributes for an asset were updated by a credentialed user. This field will not update when values are updated by calculated fields or by updates from Zone Manager. Only accounts updating assets via the CenterScape web interface or API will trigger a new timestamp. |
| Last Update User | The last user to update the attributes of an asset. |
| SSI Location | When an asset is given an assigned location the SSI Location is generated based on the deepest level in the location tree that has an SSI Rule. For example if an asset is assigned to a rack in a server room, and the server room has an SSI rule, then the Assigned Location will be the rack in the server room and the SSI Location will be the room that contains the rack. This is done for the Location Verified calculated field. Location Verified will be true if the Detected Location is either the SSI Location or the Assigned Location of an asset. SSI Location is generated by CenterScape and users can not directly update its value. |
| Detected Location Path | This is the full location tree path that an asset is detected at based on Zone Manager’s calculations. This field is generated by CenterScape and cannot be modified as its value is derived from Detected Location. For example: Location / USA / Texas / Austin / Austin Datacenter / Austin Server Room 01 / Rack 1 |
| Retired | Retired is a special required field for an Asset, but it is not presented in a regular asset form. The CenterScape web interface uses the term “Status” to filter the retired field as a basic filter, though the Retired can also be supplied as an attribute filter. When an asset is added it Retired attribute is set to “no”. Additionally, many calculated fields only apply to non-retired assets. |
| Service Date | Service date is the date an asset was first created in CenterScape. It is immutable and automatic.
|